Skip to content

Conversation

@digantdesai
Copy link
Contributor

Not making these tests XFail because there is still value in running these tests w/o validating output since we do go through a lot of other checks in the AoT flow when generating a PTE.

Tosa ref model being not installed is not the common case anyway.

Added explicit warnings (which should show through pytest) as a reminder for the comparison is being skipped.

Test plan

local testing with pytest, with and without tosa_ref_model

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 8, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13221

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures, 12 Pending, 47 Unrelated Failures

As of commit 74ebafa with merge base ec67249 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 8, 2025
@github-actions
Copy link

github-actions bot commented Aug 8, 2025

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@facebook-github-bot
Copy link
Contributor

@digantdesai has imported this pull request. If you are a Meta employee, you can view this in D79887501.

@zingo zingo added the module: arm Issues related to arm backend label Aug 8, 2025
Not making these tests XFail because there is still value in running
these tests w/o validating output since we do go through a lot of other
checks in the AoT flow when generating a PTE.

TOSA ref model being not installed is not the common case anyway.

Added explicit warnings (which should show through pytest unlike
logger) as a reminder for the comparison is being skipped.

Test: with and w/o tosa_reference_model installed locally
@facebook-github-bot
Copy link
Contributor

@digantdesai has imported this pull request. If you are a Meta employee, you can view this in D79887501.

@facebook-github-bot
Copy link
Contributor

@digantdesai has imported this pull request. If you are a Meta employee, you can view this in D79887501.

@facebook-github-bot facebook-github-bot merged commit 365d4c1 into main Aug 14, 2025
187 of 238 checks passed
@facebook-github-bot facebook-github-bot deleted the tosa_ref_model branch August 14, 2025 21:53
agrima1304 pushed a commit to agrima1304/executorch that referenced this pull request Aug 26, 2025
Differential Revision: D79887501

Pull Request resolved: pytorch#13221
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: arm Issues related to arm backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants